Add support for specifying null
values for tool fields
#850
+250
−167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the ability to specify a
null
value for nullable fields by conditionally rendering anull
checkbox when a field has anull
type in the array. If the checkbox is selected, the input will be disabled.I chose checkboxes over supporting a value of
"null"
to make behavior explicit, obvious, and not to affect cases where you actually want to send "null" as a value.Example:
Note
When reviewing, hide whitespace changes

Motivation and Context
At present, there is no way to specify a
null
value for a field.How Has This Been Tested?
Breaking Changes
No
Types of changes
Checklist